-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix specs to be compatible with forked repositories #152
Fix specs to be compatible with forked repositories #152
Conversation
Tests were coupled to a specific origin meaning that tests against forks would fail. I’ve replaced the test that checks the output of `git_remote_url` is okay into a test to check `git_remotes` returns something, and another to check that `git_remote_url` correctly interprets the output from `git_remotes`. I’ve also corrected the test doubles in later tests where (as part of jekyll#147) I had copied an incorrect bit of stubbing of `git_remote_url`. The stubbing appeared to be mimicking `git_remotes` instead. The test seemed to be passing by coincidence before. The stubbed output now matches what the function actually does.
@mrmanc Can you please explain why you made all those whitespace changes..? |
Yikes—I didn’t spot that I’d accidentally triggered my IDE’s reformatting functionality. That should be resolved now. |
The diff looks a lot better now. Thanks P.S. Ignore the failing tests in this context |
Oh, not sure what the convention is. I’ve made it more descriptive based on looking at some closed PR titles. Any better? |
Don't worry about it. I've renamed it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 👍
@jekyllbot: merge +dev |
Thank you so much!! |
You’re welcome, I’ve enjoyed these contributions 👍 |
Tests were coupled to a specific origin meaning that tests against forks would fail. I’ve replaced the test that checks the output of
git_remote_url
is okay into a test to checkgit_remotes
returns something, and another to check thatgit_remote_url
correctly interprets the output fromgit_remotes
.I’ve also corrected the test doubles in later tests where (as part of #147) I had copied an incorrect bit of stubbing of
git_remote_url
. The stubbing appeared to be mimickinggit_remotes
instead. The test seemed to be passing by coincidence before. The stubbed output now matches what the function actually does.